docs: document ALLOW_INSECURE_GIT_ACCESS for trusted local git providers#521
Open
abhikb2005 wants to merge 1 commit into
Open
docs: document ALLOW_INSECURE_GIT_ACCESS for trusted local git providers#521abhikb2005 wants to merge 1 commit into
abhikb2005 wants to merge 1 commit into
Conversation
VascoSch92
approved these changes
May 26, 2026
Member
VascoSch92
left a comment
VascoSch92
left a comment
There was a problem hiding this comment.
Just a small comment.
Otherwise, LGTM
| ### Git Provider Access | ||
| | Environment Variable | Type | Default | Description | | ||
| |---------------------|------|---------|-------------| | ||
| | `ALLOW_INSECURE_GIT_ACCESS` | boolean | `false` | Allow OpenHands to connect to git providers over plain HTTP. Set this only for trusted local or internal Gitea/Forgejo instances where HTTPS is not available. | |
Member
There was a problem hiding this comment.
The wording is slightly narrower than the actual code behavior.
In provider.py, the insecure-HTTP path triggers for any provider whose host starts with http:// (e.g. a self-hosted GitLab over plain HTTP)
if domain and domain.strip().startswith('http://'):
allow_insecure = os.environ.get('ALLOW_INSECURE_GIT_ACCESS', 'false').lower() in ('true', '1', 'yes')Could we generalize the description slightly, e.g.:
Allow OpenHands to connect to git providers over plain HTTP. Set this only for trusted local or internal git providers (such as Gitea/Forgejo) where HTTPS is not available.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds documentation for
ALLOW_INSECURE_GIT_ACCESSwhen using trusted local/internal Gitea or Forgejo instances over HTTP.Context
Related to OpenHands/OpenHands#14523.
@VascoSch92, you asked me to tag you in the PR.
Scope
This PR is intentionally docs-only.
It:
ALLOW_INSECURE_GIT_ACCESSto the environment variables reference.It does not:
Validation
ALLOW_INSECURE_GIT_ACCESS.git diff --checkpasses.npx.